SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 53394: Common Data Model tables do not update correctly when a campaign execution fails to publish in SAS® Customer Intelligence Studio

DetailsHotfixAboutRate It

If a campaign execution fails to publish in SAS Customer Intelligence Studio, new rows are not added to the Common Data Model tables CI_COMMUNICATION or CI_CELL_PACKAGE after the next successful campaign execution.

The problem occurs in a scenario similar to the following:

  1. You create a campaign by selecting Cell ► Communication ► Process (Process node). The campaign should look similar to the following:

    image label

    Note: In this image, Select is a node.

  2. Then you execute the campaign.

    At this point an entry is made in the table that shows a value of 1 for COMMUNICATION_OCCURRENCE_NO.

  3. The Process node fails, which causes the campaign execution to fail as well. When that happens, two entries then appear in the CI_CELL_PACKAGE and CI_COMMUNICATION tables. The tables have COMMUNICATION_OCCURRENCE_NO values of 1 and 2, and a COMMUNICATION_STATUS_CD value of _11.

    image label

    In order for the campaign to execute successfully, you need to modify the Process node again.

    At this point, a third entry should be added to the tables that shows a value of 3 for COMMUNICATION_OCCURRENCE_NO. However, no such entry is added to the tables. The campaign is flagged to indicate that the publish is completed for every execution, but the flag is not reset when an error occurs.

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Marketing AutomationMicrosoft® Windows® for x646.1_M16.49.3 TS1M29.4 TS1M0
Microsoft Windows 8 Enterprise x646.1_M16.49.3 TS1M29.4 TS1M0
Microsoft Windows 8 Pro x646.1_M16.49.3 TS1M29.4 TS1M0
Microsoft Windows 8.1 Enterprise 32-bit6.1_M16.49.3 TS1M29.4 TS1M0
Microsoft Windows 8.1 Enterprise x646.1_M16.49.3 TS1M29.4 TS1M0
Microsoft Windows 8.1 Pro6.1_M16.49.3 TS1M29.4 TS1M0
Microsoft Windows 8.1 Pro 32-bit6.1_M16.49.3 TS1M29.4 TS1M0
Microsoft Windows Server 2008 R26.1_M16.49.3 TS1M29.4 TS1M0
Microsoft Windows Server 2008 for x646.1_M16.49.3 TS1M29.4 TS1M0
Microsoft Windows Server 2012 Datacenter6.1_M16.49.3 TS1M29.4 TS1M0
Microsoft Windows Server 2012 R2 Datacenter6.1_M16.49.3 TS1M29.4 TS1M0
Microsoft Windows Server 2012 R2 Std6.1_M16.49.3 TS1M29.4 TS1M0
Microsoft Windows Server 2012 Std6.1_M16.49.3 TS1M29.4 TS1M0
Windows 7 Enterprise x646.1_M16.49.3 TS1M29.4 TS1M0
Windows 7 Professional x646.1_M16.49.3 TS1M29.4 TS1M0
64-bit Enabled AIX6.1_M16.49.3 TS1M29.4 TS1M0
64-bit Enabled Solaris6.1_M16.49.3 TS1M29.4 TS1M0
HP-UX IPF6.1_M16.49.3 TS1M29.4 TS1M0
Linux for x646.1_M16.49.3 TS1M29.4 TS1M0
Solaris for x646.1_M16.49.3 TS1M29.4 TS1M0
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.